Pods: Gang Scheduling & Topology awareness #494
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR introduces
Gang Scheduling(#393) in conjunction withTopology Aware Scheduling (TAS)(423) to the pods scheduler, as well as a refactoring of the overall scheduling behavior (includes #421).TODO
The code is in a working state, however the PR is kept in draft state since there is still work needed in order to get a clean integration into the project:
PodGroupSetControllerto handle the creation of pods from scheduled PGSs which is currently done by the schedulerTODOcomments throughout the codePodGroupSetsandTopologylabelsChangelog
PodGroupSet (PGS)as a newCRDwhich is used for gang scheduled workloadsinformersand state of the pod/PGS are fetched from the respectivelisterkube-schedulerPipelineDecisionControllerto reconciling pipeline stepsPodGroupSetControllerthat handles the lifecycle events ofPodGroupSetsTopologydata structure for hierarchical scheduling attempts for PGSs which is used forTAScortex/topology-rack=rack-23